Virginia Shoreline Inventory - Land Use Bank Cover

Metadata also available as

Metadata:

Identification_Information:
Citation:
Citation_Information:
Originator:
Comprehensive Coastal Inventory, Virginia Institute of Marine Science
Publication_Date: 2012
Title: Virginia Shoreline Inventory - Land Use Bank Cover
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Gloucester Point, Virginia
Publisher: Virginia Institute of Marine Science
Other_Citation_Details:
For shoreline inventories by county, please visit <http://ccrm.vims.edu/gis_data_maps/shoreline_inventories/index.html>
Online_Linkage:
<http://ccrm.vims.edu/gis_data_maps/shoreline_inventories/index.html>
Description:
Abstract:
Shoreline Situation Reports (SSR) were first generated by VIMS in the 1970's to report the condition and status of the shore lands. The SSR series were published in hardcopy on a county by county basis for each Tidewater Virginia localities. The reports were intended to assist planners, managers, and regulators in decisions pertaining to management of coastal areas and natural resources therein. This Shoreline Inventory report continues a process which updates and expands the earlier reports. Data collected reports conditions surveyed in the immediate riparian zone, the bank, and along the shoreline. This dataset is the result of combining the most recent digital shoreline inventories for Virginia.
Purpose: To inventory Virginia's tidal shoreline conditions.
Supplemental_Information:
There are three shapefiles that are part of the Shoreline Inventory database: *_lubc, *_astru, *_sstru. The _lubc (land use and bank cover) is a linear shapefile containing data about land use, bank height, erosion, bank cover, Phragmites australis, tree fringe, canopy overhang, marsh, and beach status along the shoreline. The _sstru (shoreline structures) is a linear shapefile delineating hard structures at the shoreline (bulkhead, breakwater, dilapidated bulkhead, debris, jetty, marina, marsh toe revetment, unconventional, riprap, groin fields). The _astru (access structures) is a point shapefile with locations of docks, ramps,a dilapidated docks, outfalls, and boathouses. The attributes of these three shapefiles are explained in the Entity and Attribute Information section below.
Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1998
Ending_Date: 2012
Currentness_Reference: ground condition at time of survey
Status:
Progress: Ongoing
Maintenance_and_Update_Frequency: Unknown
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -77.658340
East_Bounding_Coordinate: -75.256723
North_Bounding_Coordinate: 39.080593
South_Bounding_Coordinate: 36.525828
Keywords:
Theme:
Theme_Keyword_Thesaurus: none
Theme_Keyword: Shoreline conditions
Theme_Keyword: Riparian Land use
Theme_Keyword: Shoreline Inventory
Place:
Place_Keyword_Thesaurus: none
Place_Keyword: Virginia
Place_Keyword: Chesapeake Bay
Place_Keyword: Accomack County
Place_Keyword: Caroline County
Place_Keyword: City of Chesapeake
Place_Keyword: City of Portsmouth
Place_Keyword: Essex County
Place_Keyword: Fairfax and City of Alexandria
Place_Keyword: Gloucester County
Place_Keyword: Henrico County
Place_Keyword: King and Queen County
Place_Keyword: King George County
Place_Keyword: King William County
Place_Keyword: Lancaster County
Place_Keyword: Lynnhaven Bay
Place_Keyword: Mathews County
Place_Keyword: Middlesex County
Place_Keyword: New Kent Countiy
Place_Keyword: Newport News
Place_Keyword: Norfolk
Place_Keyword: Northampton County
Place_Keyword: Northumberland County
Place_Keyword: Poquoson
Place_Keyword: Prince William
Place_Keyword: Richmond County
Place_Keyword: Stafford County
Place_Keyword: Virginia Beach
Place_Keyword: Westmoreland County
Place_Keyword: Pagan River
Place_Keyword: York County
Access_Constraints: none
Use_Constraints:
These data should not be used for jurisdictional permit determinations beyond providing general shoreline condition or status information. These data have not been surveyed to property boundaries.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Marcia Berman
Contact_Organization: Virginia Institute of Marine Science (VIMS)
Contact_Position: Director of Comprehensive Coastal Inventory Program (CCI)
Contact_Address:
Address_Type: P.O. Box 1346
Address: Greate Road
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Contact_Voice_Telephone: 804-684-7188
Contact_Facsimile_Telephone: 804-684-7179
Contact_Electronic_Mail_Address: marcia@vims.edu
Native_Data_Set_Environment:
Microsoft Windows Vista Version 6.1 (Build 7601) Service Pack 1; ESRI ArcCatalog 9.3.1.3500
Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
The attributes were compared to original GPS data logs for accuracy. Errors were corrected where noted.
Completeness_Report:
This inventory targets tidal shoreline only. Access by boat is required for field surveys. Remote sensing techniques are used in areas where water depths are too shallow for access or where unmanaged, undeveloped shoreline persists along very long reaches. This would include headwaters of tidal creeks, and natural areas along park and conservation lands.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report:
Shoreline attributes recorded with a GPS unit as the boat moves along the shoreline has a horizontal accuracy of +/- 5 meters. Data was transferred from the GPS boat track to an existing digital shoreline coverage by projecting data to the shoreline at a 90 degree angle from the boat track. Rectified imagery were used as a background coverage to aid in data positioning. Land use features were placed along the shore so changes in land use were coincident with changes illustrated in the imagery. Positional accuracy for data that has been corrected with imagery which has a resolution of 2 meters or better. Accuracy limits of the field collected data, however, are set at 5 meters due to the short occupancy of GPS units. In many cases the image correction yields a final positional accuracy much closer to 2 meters or less, depending on image resolution.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Comprehensive Coastal Inventory Program, Virginia Institute of Marine Science
Publication_Date: 1991
Title: Mean High Water Shoreline Position, Virginia
Geospatial_Data_Presentation_Form: vector digital data
Source_Scale_Denominator: 24,000
Type_of_Source_Media: mylar
Source_Time_Period_of_Content:
Time_Period_Information:
Range_of_Dates/Times:
Beginning_Date: 1964
Ending_Date: 1987
Source_Currentness_Reference: date of USGS map
Source_Citation_Abbreviation: SHL
Source_Contribution:
Digital shoreline serves as base shoreline for shoreline conditions for the following counties: King and Queen, King William, Middlesex, and Poquoson.
Source_Information:
Source_Citation:
Citation_Information:
Originator: U.S. Geological Survey
Publication_Date: 1994
Title: Digital Orthophoto Quadrangles
Geospatial_Data_Presentation_Form: remote-sensing image
Publication_Information:
Publication_Place: Reston, VA
Publisher: U.S. Geological Survey
Type_of_Source_Media: color infra-red digital imagery
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 1994
Source_Currentness_Reference: ground condition
Source_Citation_Abbreviation: DOQQ
Source_Contribution:
Serves as a background coverage in some of the map portfolios. Used to accurately position land use and cover data. Used to create a new digital shoreline coverage that serves as the base shoreline for shoreline conditions. Counties that used this shoreline: Accomack, Caroline, Essex, Lancaster, Northumberland, Richmond, and Pagan River. Counties that used this in conjunction with another shoreline: Gloucester, King and Queen, King George, King William, Middlesex, New Kent, Newport News, and Poquoson.
Source_Information:
Source_Citation:
Citation_Information:
Originator: City of Norfolk
Publication_Date: 1999
Title: Norfolk Hydrology
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Norfolk, VA
Publisher: City of Norfolk
Type_of_Source_Media: digital orthophotographs
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 1999
Source_Citation_Abbreviation: City of Norfolk
Source_Contribution: Provided the base shoreline for the City of Norfolk
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 2003
Title: Virginia Base Map Program (VBMP)
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Richmond, VA
Publisher: Virginia Geographic Information Network
Source_Scale_Denominator: 4800
Type_of_Source_Media: DVD
Source_Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2002
Source_Citation_Abbreviation: VBMP 2002
Source_Contribution:
Imagery (2002) serves as a background in the map portfolio. Imagery is used to update land use and structure data as well as to remotely code areas not previously surveyed in the field. The VBMP shoreline was also used and adjusted using the imagery where needed. This shoreline was used in the following counties: Gloucester, Lynnhaven Bay, Stafford, and Westmoreland.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 2006/2007
Title: Virginia Base Map Program Imagery and Hydrology
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Richmond, VA
Source_Citation_Abbreviation: VBMP 2006/07
Source_Contribution:
Imagery (2007) serves as a background in the map portfolio. Imagery is used to update land use and structure data as well as to remotely code areas not previously surveyed in the field. The VBMP shoreline was also used and adjusted using the imagery where needed. This shoreline was used in the following counties: City of Chesapeake, City of Portsmouth, King George, New Kent, Newport News, and Mathews.
Source_Information:
Source_Citation:
Citation_Information:
Originator:
Commonwealth of Virginia, through Virginia Geographic Network Division of its Department of Technology Planning (VGIN)
Publication_Date: 2009, 2011
Title: Virginia Base Mapping Program (VBMP)
Publication_Information:
Publication_Place: Richmond, VA
Source_Citation_Abbreviation: VBMP 2009, 2011
Source_Contribution:
Imagery (2009, 2011) serves as a background in the map portfolio. Used to accurately position land use and land cover data. Provided a new digital shoreline coverage that serves as the base shoreline for shoreline conditions. Used in the following counties: City of Virginia Beach, Henrico, and Northampton.
Process_Step:
Process_Description:
Data was collected by a three-person field crew (1989-2001) or a two-person field crew (2002 to present). From 2002 to 2012 a two-person crew consisted of one person collecting land use and bank condition data and one boat operator also collecting shoreline features using two hand-held Trimble GeoExplorers GPS Units, while navigating along the shoreline. A data dictionary designed for the inventory was installed on each GPS Unit. One data collector records natural features including land use, bank height, presence of marsh or beach, and shoreline stability. A second person collects data on the hardened structures: riprap, bulkheads, docks, boatramps, etc. Point features (docks, boathouses, ramps) were surveyed with a six second observation recorded at 1 reading/second. Linear features were surveyed kinematically at a rate of one observation every 3 seconds. Begining in 2012 the two-person crew consists of a boat operator and one data surveyor. The boat operator navigates the boat to follow the shoreline geometry. The data surveyor uses a geo-referenced video camera. The Red Hen System provides hardware and software to collect geo-referenced video and photo data in the field. A standard video camera (sony ACC-HDV7) is interfaced with a GPS antennae via the Red Hen hardware device - VMS 300. VMS 300 converts GPS data into audio signals, which are sent to a video camera through its microphone input connector. As the video is recorded, GPS data are transmitted once per second to the video camera by VMS 300. Each GPS location is linked with a time code on the video. Therefore, the survey is a set of videos containing geographically referenced shoreline data.
Process_Date: 1998 - present
Process_Step:
Process_Description:
Data from the GPS units were postprocessed using Trimble Pathfinder Office software. Postprocessing included differential correction using CORS (Continuous Operating Reference Stations) data. Corrected data are converted to shape files for further processing in the GIS environment.
Process_Date: 1998 - 2012
Process_Step:
Process_Description:
In the ArcMap environment, boat-track arcs and points were manually shifted to the base shoreline. Arcs were split and moved to locations on the shoreline perpendicular to the original locations on the boat-track. Points were also moved to locations on the shoreline perpendicular to the original locations on the boat-track. Shoreline arc segments and points were coded, and the shapefiles were visually checked for attribute accuracy between coded shoreline and boat-track data.
Process_Date: 1998 - present
Process_Step:
Process_Description:
The shoreline for Northampton was extracted from the VGIN LiDar derived, hydro flattened DEM for the Eastern Shore using the ArcMap contour tool. Bank height was generated from the VBMP. The 0, 5, 10 and 30 foot contours were derived from the VBMP Eastern Shore hydrologically correct DEM based on the 2010 LiDar survey, using the raster surface contour tool. It was decided that the bank would be within 10 meters of the 0 contour except on some beaches where the bank was visually further away. 10 meter buffers were created for the 5, 10 and 30 foot contours. Each of these buffers was run with the 0 contour in the intersect tool to make files showing where the contours were within 10 meters of the 0. In no case did the 30 foot contour intersect 0. The 3 files for 0, 5, and 10 were run in the identity tool to make the final file showing bank height feature attributes of 0-5, 5-10, and 10-30. This was merged with the land use data and became an attribute in the shapefile.
Process_Date: 2011
Process_Step:
Process_Description:
For Henrico, and parts of Virginia Beach (Broad Bay and Rudy Inlet) data were logged using a geo-referenced video camera.
Process_Date: 2012
Process_Step:
Process_Description:
For tributaries surveyed in the field using GPS referenced videography, the proprietary software associated with the Red Hen System is used for post processing: Pixpoint and GeoVideo for GIS. The PixPoint software package is used to generate a point shapefile containing points representing locations of geo-referenced still photos taken during the survey. GeoVideo software package is an ArcGIS extension. It is a desktop mapping application that brings the geo-referenced video directly into the ArcGIS environment. This software enables users to digitally map videos using GPS coordinates. After the videos are downloaded to the computer, the GeoVideo software is used to generate a point shapefile which is geotagged to the precise track of the video survey. This shapefile is a representation of the survey track. Along with the video link, it enables GIS personnel to code the shoreline conditions in ArcMap based on what is viewed in the video.
Process_Date: 2012
Process_Step:
Process_Description:
Land use, point structure, and linear structure locations were digitally checked and repositioned if necessary with imagery displayed in the background. Coding takes place in the ArcMap environment using coding, heads-up digitizing, and photo-interpretation techniques. Areas inaccessible by boat due to low tide were coded based on features observed on the imagery. The "remote" coded areas were given the item REMOTE = "yes" to distinquish them from GPS collected data. Background image quality depends upon imagery available the year inventory was published. Begining in 2011/2012 recent high resolution color infra-red and natural color imagery (2009 and 2011) with a resolution of 1 meter or better is used along with Bing oblique imagery to identify and code the shoreline for shoreline attributes.
Process_Date: 1998 - present
Process_Step:
Process_Description:
Begining in 2012 marsh data is being collected separately and is no longer part of the shoreline inventory "lubc" shapefile. Marsh data (including phragmites information) will be in served in the updated Tidal Marsh Inventory (TMI): <http://ccrm.vims.edu/gis_data_maps/static_maps/gis/tmi_updated.html>
Process_Date: 2012
Process_Step:
Process_Description: County inventories were merged together.
Process_Date: 2009 - present
Process_Step:
Process_Description: Metadata imported.
Source_Used_Citation_Abbreviation: C:\Users\tamia\AppData\Local\Temp\xmlC109.tmp
Process_Date: 20130607
Process_Time: 09434600
Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: String
Point_and_Vector_Object_Count: 76777
Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Grid_Coordinate_System:
Grid_Coordinate_System_Name: Universal Transverse Mercator
Universal_Transverse_Mercator:
UTM_Zone_Number: 18
Transverse_Mercator:
Scale_Factor_at_Central_Meridian: 0.999600
Longitude_of_Central_Meridian: -75.000000
Latitude_of_Projection_Origin: 0.000000
False_Easting: 500000.000000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.000000
Ordinate_Resolution: 0.000000
Planar_Distance_Units: meters
Geodetic_Model:
Horizontal_Datum_Name: North American Datum of 1983
Ellipsoid_Name: Geodetic Reference System 80
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257222
Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: va_lubc_2012_Oct2012
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: LENGTH
Attribute:
Attribute_Label: EROSION
Attribute_Definition: bank erosion
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: low
Enumerated_Domain_Value_Definition: minimal erosion on bank face
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: high
Enumerated_Domain_Value_Definition: Includes slumping, scarps, and exposed roots
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: undercut
Enumerated_Domain_Value_Definition: Erosion at the base of the bank
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: erosional
Enumerated_Domain_Value_Definition: includes slumping, roots exposed, no structure, trees down.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: erosional/undercut
Enumerated_Domain_Value_Definition:
includes slumping, roots exposed, no structure, trees down, and erosion at base of bank
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: stable
Enumerated_Domain_Value_Definition: no sign of erosion; stabliized by vegetation or a structure
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: stable/undercut
Enumerated_Domain_Value_Definition: bank is stable but there is erosion at base of bank
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: transitional
Enumerated_Domain_Value_Definition:
partial coverage, areas where there are clearly signs of erosion, but not fully erosional
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: transition/undercut
Enumerated_Domain_Value_Definition:
eroion at base of bank and bank face has partial coverage, or is showing signs of erosion (but not fully erosional)
Attribute:
Attribute_Label: MARSH
Attribute_Definition: presence of marsh
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Extensive
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Embayed
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Fringe
Enumerated_Domain_Value_Definition:
narrow strip of marsh vegetation extending along the shoreline. he vegetation must be relatively well established, although not necessarily densely populated.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Fringe 10-15
Enumerated_Domain_Value_Definition: fringe marsh 10-15 feet wide
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Fringe 5-10
Enumerated_Domain_Value_Definition: fringe marsh 5-10 feet wide
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Fringe <5
Enumerated_Domain_Value_Definition: fringe marsh <5 feet wide
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Fringe >15
Enumerated_Domain_Value_Definition: Fringe marsh > 15 feet wide
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: marsh is present
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Yes(No_Erosion)
Enumerated_Domain_Value_Definition: marsh present at bank toe with no obvious signs of erosion
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: Yes(Erosion)
Enumerated_Domain_Value_Definition:
marsh present at bank toe. Marsh edge is eroding or showing vegetation loss
Attribute:
Attribute_Label: BEACH
Attribute_Definition: presence of beach
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: Presence of a sand beach
Attribute:
Attribute_Label: PHRAG
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: Presence of the grass Phragmites australis
Attribute:
Attribute_Label: CANOPY_OVE
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: Branches from trees along the shore overhang the water
Attribute:
Attribute_Label: TREE_FRING
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition:
Trees along the shore is present in conjuncture with the dominant land use
Attribute:
Attribute_Label: HEIGHT
Attribute_Definition: bank height
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 0-5
Enumerated_Domain_Value_Definition: 0-5 ft. from the toe to the edge of the fastland
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 5-10
Enumerated_Domain_Value_Definition: 5-10 ft. from the toe to the edge of the fastland
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: 10-30
Enumerated_Domain_Value_Definition: 10-30 ft. from the toe to the edge of the fastland
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: >30
Enumerated_Domain_Value_Definition: >30 ft. from the toe to the edge of the fastland
Attribute:
Attribute_Label: COVER
Attribute_Definition: bank cover
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: bare
Enumerated_Domain_Value_Definition: <25% cover: vegetative or structural cover
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: partial
Enumerated_Domain_Value_Definition: 25% to 75% cover: vegetative or structural cover
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: total
Enumerated_Domain_Value_Definition: >75% cover: vegetative or structural cover
Attribute:
Attribute_Label: GPS_DATE
Attribute_Definition: Date of data capture
Attribute:
Attribute_Label: REMOTE
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: yes
Enumerated_Domain_Value_Definition: Data coded in the lab using background imagery
Attribute:
Attribute_Label: FEATURE
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: agriculture
Enumerated_Domain_Value_Definition: Croplands
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: bare
Enumerated_Domain_Value_Definition: Lot cleared to bare soil
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: commercial
Enumerated_Domain_Value_Definition:
Includes small and moderate business operations, recreational facilities
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: educational/school
Enumerated_Domain_Value_Definition: Includes public and private facilities
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: family dwelling
Enumerated_Domain_Value_Definition: Single family dweeling
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: forest
Enumerated_Domain_Value_Definition: Stands greater than 18 ft. high/ width greater tha 30 ft.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: grass
Enumerated_Domain_Value_Definition: Includes grassland and pastures
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: industrial
Enumerated_Domain_Value_Definition: Includes large industry and manufacturing operations
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: military
Enumerated_Domain_Value_Definition: Includes all military installations
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: multifamily
Enumerated_Domain_Value_Definition: Multi family dwellings includes condominiums, and apartments
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: paved
Enumerated_Domain_Value_Definition:
Areas where roads or parking areas are adjacent to the shoreline
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: residential
Enumerated_Domain_Value_Definition: Includes single and multi-family dwellings
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: scrub-shrub
Enumerated_Domain_Value_Definition: Stands less than 18 ft.
Attribute_Domain_Values:
Enumerated_Domain:
Enumerated_Domain_Value: timbered
Enumerated_Domain_Value_Definition: Clear-cuts
Attribute:
Attribute_Label: COUNTY
Attribute_Definition: county or waterbody inventoried
Attribute:
Attribute_Label: SURVEYED
Attribute_Definition: year data collected
Attribute:
Attribute_Label: marsh_orig
Attribute_Definition: original coding for MARSH
Attribute:
Attribute_Label: beach_orig
Attribute_Definition: original coding for BEACH
Attribute:
Attribute_Label: SHORELINE
Attribute_Definition: base shoreline used (refer to lineage)
Overview_Description:
Entity_and_Attribute_Overview:
Two other shapefiles combine with _lubc to complete the Shoreline Inventory. The complete set includes _lubc, _astru, and _sstru. Attributes in the _lubc file include: FEATURE or land use may contain the following values: agriculture, bare, commercial, educational/school, family dwelling, forest, grass, industrial, military, multifamily dwelling, paved, residential, scrub-shrub, and timbered; HEIGHT is the bank height with 0 - 5 feet, 5 - 10 feet, and 10 - 30 feet, and >30; EROSION or bank erosion can have the values: low, high, undercut, erosional, erosional/undercut, stable, stable/undercut, transitional, or transition/undercut; MARSH values may be yes, no, yes(erosion), yes(no_erosion), embayed, extensive, and fringe <5, 5-10, 10-15 and >15; Beach values are the presence or absence of beach where "yes" indicates a beach and "no" or a null value indicates no beach; Cover (bank cover) is defined as bare, partial, or total; Tree Fringe is coded as 'Yes" for the presence of a tree buffer along the shoreline; Canopy overhang is "yes" if the tree fringe overhangs the shoreline; and REMOTE refers to how the data was gathered: a blank value indicates the data was collected with the GPS unit, a "y" indicates that the shoreline attributes where determined from imagery. Phragmites australis is coded as 'yes' where its presence is noted. Attributes in the _astru (access structure shapefile) are: PNTSTRUC contains access structures such as boathouse, dock, dilapidated dock, outfall, and public or private ramp; and REMOTE. Attributes found in the _sstru shapefile are: STRUCTURE (erosion control)with values such as breakwater, bulkhead, debris, dilapidated bulkhead, groinfield, jetty, marina, marsh toe revetment, military wharf, miscellaneous, riprap, seawall, shipyard, unconventional, and wharf; and REMOTE.
Distribution_Information:
Resource_Description: Downloadable Data
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 97.839
Metadata_Reference_Information:
Metadata_Date: 20130607
Metadata_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Tami Rudnicky
Contact_Organization: Virginia Institute of Marine Science (VIMS)
Contact_Position: GIS Programmer/Analyst
Contact_Address:
Address_Type: P.O. Box 1346
Address: Greate Road
City: Gloucester Point
State_or_Province: Virginia
Postal_Code: 23062
Contact_Voice_Telephone: 804-684-7181
Contact_Facsimile_Telephone: 804-684-7179
Contact_Electronic_Mail_Address: tamia@vims.edu
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile
Generated by mp version 2.9.6 on Fri Jun 07 09:46:31 2013